Systems and methods of utilization of a hydraulic fracturing unit profile to operate hydraulic fracturing units

ABSTRACT

A methods and system to operate hydraulic fracturing units may include utilizing hydraulic fracturing unit profiles. The system may include hydraulic fracturing units may include various components. The components may include an engine and associated local controller and sensors, a transmission connected to the engine, transmission sensors, and a pump connected to the transmission and powered by the engine via the transmission and associated local controller and sensors. A supervisory controller may control the hydraulic fracturing units. The supervisory controller may be in communication with components of each hydraulic fracturing unit. The supervisory controller may include instructions to, for each hydraulic fracturing units, obtain hydraulic fracturing unit parameters, determine a hydraulic fracturing unit health assessment, and build a hydraulic unit profile including the health assessment and parameters. The supervisory controller may, based on the health assessment, determine the hydraulic fracturing unit&#39;s capability to be operated at a maximum power output.

PRIORITY CLAIM

This is a continuation of U.S. Non-Provisional application Ser. No. 17/892,479, filed Aug. 22, 2022, titled “SYSTEMS AND METHODS OF UTILIZATION OF A HYDRAULIC FRACTURING UNIT PROFILE TO OPERATE HYDRAULIC FRACTURING UNITS,” which is a continuation of U.S. Non-Provisional application Ser. No. 17/301,475, filed Apr. 5, 2021, titled “SYSTEMS AND METHODS OF UTILIZATION OF A HYDRAULIC FRACTURING UNIT PROFILE TO OPERATE HYDRAULIC FRACTURING UNITS,” now U.S. Pat. No. 11,466,680, issued Oct. 11, 2022, which claims priority to and the benefit of, U.S. Provisional Application No. 62/705,628, filed Jul. 8, 2020, titled “USE OF A PUMP PROFILER AND HEALTH MONITORING FUNCTION TO OPERATE HYDRAULIC FRACTURING PUMPS AND ASSOCIATED METHODS,” and U.S. Provisional Application No. 62/705,357, filed Jun. 23, 2020, titled “THE USE OF A PUMP PROFILER AND HEALTH MONITORING FUNCTION TO OPERATE HYDRAULIC FRACTURING PUMPS AND ASSOCIATED METHODS,” the disclosures of which are incorporated herein by reference in their entireties.

TECHNICAL FIELD

The present disclosure relates to methods and systems for enhancing operation of hydraulic fracturing equipment at a hydraulic fracturing wellsite.

BACKGROUND

Hydrocarbon exploration and energy industries employ various systems and operations to accomplish activities including drilling, formation evaluation, stimulation and production. Hydraulic fracturing may be utilized to produce oil and gas economically from low permeability reservoir rocks or other formations, for example, shale, at a wellsite. During a hydraulic fracturing stage, slurry may be pumped, via hydraulic fracturing pumps, under high pressure to perforations, fractures, pores, faults, or other spaces in the reservoir rocks or formations. The slurry may be pumped at a rate faster than the reservoir rocks or formation may accept. As the pressure of the slurry builds, the reservoir rocks or formation may fail and begin to fracture further. As the pumping of the slurry continues, the fractures may expand and extend in different directions away from a well bore. Once the reservoir rocks or formations are fractured, the hydraulic fracturing pumps may remove the slurry. As the slurry is removed, proppants in the slurry may be left behind and may prop or keep open the newly formed fractures, thus preventing the newly formed fractures from closing or, at least, reducing contracture of the newly formed fractures. Further, after the slurry is removed and the proppants left behind, production streams of hydrocarbons may be obtained from the reservoir rocks or formation.

For a wellsite, a plurality of hydraulic fracturing stages may be performed. Further, each hydraulic fracturing stage may require configuration of many and various hydraulic fracturing equipment. For example, prior to a next hydraulic fracturing stage, an operator or user may enter multiple data points for that next hydraulic fracturing stage for each piece of equipment, such as, for hydraulic fracturing pumps, a blender, a chemical additive unit, a hydration unit, a conveyor, and/or other hydraulic fracturing equipment located at the wellsite. As each hydraulic fracturing stage arises, hydraulic fracturing units may be utilized. After hydraulic fracturing stages, hydraulic fracturing units may require or may soon after require maintenance, based on several factors, such as prior use or fluid/consumable levels. Each hydraulic fracturing unit may require a user to physically inspect the units to determine a maintenance schedule. Such tasks may be inaccurately interpreted and time consuming.

SUMMARY

Accordingly, Applicant has recognized a need for methods and system to enhance operation of hydraulic fracturing equipment at a hydraulic fracturing wellsite. The present disclosure may address one or more of the above-reference drawbacks, as well as other potential drawbacks.

As referenced above, due to a large number of hydraulic fracturing stages and the large number of hydraulic fracturing equipment associated with the hydraulic fracturing stages, monitoring hydraulic fracturing equipment health and determining potential maintenance periods may be difficult, complex, and time-consuming, and may introduce error, for example, utilizing equipment requiring maintenance. Further, missing maintenance may result in equipment life being reduced, thus resulting in a potential breakdown of the equipment.

The present disclosure generally is directed to methods and systems for operating hydraulic fracturing equipment at a hydraulic fracturing wellsite. In some embodiments, the methods and systems may provide for efficient and enhanced operation of the hydraulic fracturing equipment, for example, during setup, maintenance, or as through hydraulic fracturing equipment stages or operations.

According to an embodiment of the disclosure, a wellsite hydraulic fracturing system may include one or more hydraulic fracturing units. The one or more hydraulic fracturing units, when positioned at a hydraulic fracturing wellsite, may be configured to provide a slurry to a wellhead in hydraulic fracturing pumping stages. Each of the one or more hydraulic fracturing units may include an internal combustion engine, a local controller for the internal combustion engine, and engine sensors disposed on the internal combustion engine. Each of the one or more hydraulic fracturing units may include a transmission connected to the internal combustion engine, transmission sensors disposed on the transmission, and a local controller for the transmission. The hydraulic fracturing unit may include a pump connected to the transmission. The pump may be powered by the internal combustion engine via the transmission. The hydraulic fracturing unit may include a local controller for the pump and pump sensors disposed on the pump.

The wellsite hydraulic fracturing system may include a supervisory controller to control the hydraulic fracturing units, the supervisory controller being positioned in signal communication with a terminal and, for each of the one or more hydraulic fracturing units, the engine sensors, the transmission sensors, the pump sensors, the local controller for the internal combustion engine, and the local controller for the pump. The supervisory controller may include a processor and memory storing instructions. The processor may be configured to execute instructions stored in memory. The instructions, when executed by the processor, may be configured to, for each of the one or more hydraulic fracturing units, obtain hydraulic fracturing unit parameters from the local controller of the internal combustion engine, the local controller of the pump, the engine sensors, the transmission sensors, and the pump sensors. The hydraulic fracturing unit parameters may include one or more of hydraulic fracturing unit data, a hydraulic fracturing unit configuration, a hydraulic fracturing health rating, and a hydraulic fracturing unit alarm history. The supervisory controller may include instructions, when executed by the processor, to determine a hydraulic fracturing unit health assessment for each of the one or more hydraulic fracturing units based on, at least in part, the hydraulic fracturing unit data, the hydraulic fracturing unit configuration, the hydraulic fracturing health rating, and the hydraulic fracturing unit alarm history. The supervisory controller may include instructions, when executed by the processor, to build a hydraulic unit profile for each of the one or more with the hydraulic fracturing units to include the hydraulic fracturing unit health assessment and hydraulic fracturing unit parameters. The supervisory controller may, based on a hydraulic fracturing unit's hydraulic fracturing health assessment, determine the hydraulic fracturing unit's capability to be operated at a maximum power output.

According to another embodiment of the disclosure, a supervisory controller for a hydraulic fracturing system may include a first control output in signal communication with one or more pump controllers, each pump controller being included on a pump and each pump being included on a hydraulic fracturing unit. The supervisory controller may be configured to, for each of the one or more pump controllers, obtain a set of pump information. The pump information may include one or more of the number of hours of use of the pump, the pump's plunger size, the pump's stroke size, the pump's maximum speed, the pump's health efficiency, and/or an age of the pump. The supervisory controller may include a second control output in signal communication with one or more hydraulic fracturing unit controllers, each hydraulic fracturing unit controller being included on a hydraulic fracturing unit. The supervisory controller may be configured to, for each of the one or more hydraulic fracturing unit controllers, obtain a set of maintenance data. The set of maintenance data may include one or more of the number of hours to next engine maintenance, the number of hours to next transmission maintenance, an oil change log, pump valve and seat (V&S) hours, packing hours, total pump strokes, average V&S hours, and average packing hours. As will be understood by those skilled in the art, each of the one or more hydraulic fracturing unit controllers may include one or more alarm conditions to be communicated to the supervisory controller. The supervisory controller may be configured to, for each of the one or more hydraulic fracturing unit controllers, obtain a set of operation data. The operation data may include one or more of the maximum hydraulic power produced during a previous hydraulic fracturing stage, a maximum hydraulic power utilized, a minimum hydraulic power utilized, an average hydraulic power, a maximum pressure produced, a maximum flow produced, a maximum pump speed, and/or a user override register. The supervisory controller may be configured, for each of the one or more hydraulic fracturing unit controllers, to obtain a set of equipment health ratings. The equipment health ratings may include one or more of the engine health, engine power rating based on engine health, transmission health, transmission deration based on health, pump health, and/or pump deration based on health. The supervisory controller may be configured to, for each of the one or more hydraulic fracturing unit controllers, obtain a set of equipment configurations. The set of equipment configurations may include one or more of engine model, engine serial number, transmission model, transmission serial number, pump model, pump serial number, fluid end model, and/or fluid end serial number. The supervisory controller may be configured to, for each of the one or more hydraulic fracturing unit controllers, obtain a set of equipment alarm history. The set of equipment alarm history may include one or more of life reduction event counter total, life reduction event for current week, pump cavitation event counter total, pump cavitation event counter for current week, pump pulsation event counter total, pump pulsation event counter for current week, emergency shutdown counter total, and/or emergency shutdown counter for current week. The supervisory controller may include a third control output in signal communication with one or more engine controllers, each engine controller being included on an engine and each engine being included on the hydraulic fracturing unit. The supervisory controller may be configured to, for each of the one or more engine controllers, obtain a set of engine information. The set of engine information may include one or more of the number of hours of use of the engine, the engine's available power, the engine's installation age, and/or the engine's efficiency health. The supervisory controller may include a fourth control output in signal communication with one or more transmission controllers, each transmission controller being included on a transmission and each transmission being included on the hydraulic fracturing unit. The supervisory controller may be configured to, for each of the one or more transmission controllers, obtain a set of transmission information. The set of transmission information may include the number of hours of use of the transmission, the transmission's installation age, and/or the transmission's efficiency health. The supervisory controller may include a terminal input/output socket in signal communication with a terminal. In response to a determination that pump information, maintenance data, operation data, equipment health ratings, equipment configuration, equipment health ratings, equipment alarm history, and engine information for each of the hydraulic fracturing units is received, the supervisory controller may be configured to build a pump profile for each of the hydraulic fracturing units. Each pump profile may include the pump information, maintenance data, operation data, equipment health ratings, equipment configuration, equipment alarm history, and engine information. Further, the supervisory controller may be configured to determine a health assessment for each of the hydraulic fracturing units, based on, at least in part, the equipment health ratings and the pump profile for each of the hydraulic fracturing units. Further still, the supervisory controller may be configured to add the health assessment to the pump profile. The supervisory controller may be configured to determine which of the one or more hydraulic fracturing units to utilize in a hydraulic fracturing operation based on the pump profile.

According to another embodiment of the disclosure, a method of utilizing a pump profile to operate hydraulic fracturing pumps for a hydraulic fracturing system may include determining if one or more pump controllers are available. Each of the one or more pump controllers may be associated with a pump of a hydraulic fracturing unit. The method may also include, in response to an availability of one or more pump controllers and for each pump associated with the one or more pump controllers, obtaining pump assembly data, pump maintenance data, and pump event and alarm history data. The method may further include determining a pump maintenance cycle based on the pump maintenance data and pump event and alarm history data. The method also may include determining maximum pump flow, maximum pump pressure, and maximum pump speed, indicated by, for example, rotations per minute (RPM), based on pump assembly data, pump maintenance data, and pump event and alarm history data.

The method may further include determining if one or more engine controllers are available. Each of the one or more engine controllers may be associated with an engine of the hydraulic fracturing unit. The method still further may include, in response to an availability of one or more engine controllers and for each engine associated with the one or more engine controllers, obtaining engine assembly data, engine maintenance data, and engine event and alarm history data. The method also may include determining life expectancy of consumables associated with the engine based on the engine maintenance data and engine event and alarm history data. The method may further include determining engine maintenance cycles based on the pump maintenance data and pump even and alarm history data. The method also may include determining maximum power output based on engine assembly data, engine maintenance data, and pump event and alarm history data. The method may include determining which of the hydraulic fracturing units to utilize for a hydraulic fracturing operation based on each hydraulic fracturing unit profile.

The method further may include building a hydraulic fracturing unit profile for each of the hydraulic fracturing units, including pump and engine data and determined characteristics. The pump and engine data and determined characteristics may include one or more of (a) pump assembly data, (b) pump maintenance data, (c) pump event and alarm history data, (d) the pump maintenance cycle, (e) the maximum pump flow, (f) the maximum pump pressure, (g) the maximum pump speed, (h) engine assembly data, (i) engine maintenance data, (j) engine event and alarm history data, (k) the engine maintenance cycle, and/or (1) the maximum power output.

Still other aspects and advantages of these embodiments and other embodiments, are discussed in detail herein. Moreover, it is to be understood that both the foregoing information and the following detailed description provide merely illustrative examples of various aspects and embodiments, and are intended to provide an overview or framework for understanding the nature and character of the claimed aspects and embodiments. Accordingly, these and other objects, along with advantages and features of the present disclosure, will become apparent through reference to the following description and the accompanying drawings. Furthermore, it is to be understood that the features of the various embodiments described herein are not mutually exclusive and may exist in various combinations and permutations.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the embodiments of the present disclosure, are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure, and together with the detailed description, serve to explain principles of the embodiments discussed herein. No attempt is made to show structural details of this disclosure in more detail than may be necessary for a fundamental understanding of the embodiments discussed herein and the various ways in which they may be practiced. According to common practice, the various features of the drawings discussed below are not necessarily drawn to scale. Dimensions of various features and elements in the drawings may be expanded or reduced to more clearly illustrate embodiments of the disclosure.

FIG. 1 is a top plan schematic view of an example wellsite hydraulic fracturing system, according to an embodiment of the disclosure;

FIG. 2A and FIG. 2B are block diagrams of an example controller connected to backside equipment, hydraulic fracturing pumps, a display, and a computing device according to an embodiment of the disclosure;

FIG. 3A and FIG. 3B are flowcharts of an example method of utilizing a pump profile to operate hydraulic fracturing pumps for a wellsite hydraulic fracturing system, according to an embodiment of the disclosure;

FIG. 4 is a block diagram of a wellsite hydraulic fracturing system, according to an embodiment of the disclosure;

FIG. 5 is a representation of an example pump profile, according to an embodiment of the disclosure;

FIG. 6 is another representation of an example pump profile, according to an embodiment of the disclosure; and

FIG. 7 is yet another representation of an example pump profile, according to an embodiment of the disclosure.

DETAILED DESCRIPTION

The present disclosure will now be described more fully hereinafter with reference to example embodiments thereof with reference to the drawings in which like reference numerals designate identical or corresponding elements in each of the several views. These example embodiments are described so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Features from one embodiment or aspect may be combined with features from any other embodiment or aspect in any appropriate combination. For example, any individual or collective features of method aspects or embodiments may be applied to apparatus, product, or component aspects or embodiments and vice versa. The disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. As used in the specification and the appended claims, the singular forms “a,” “an,” “the,” and the like include plural referents unless the context clearly dictates otherwise. In addition, while reference may be made herein to quantitative measures, values, geometric relationships or the like, unless otherwise stated, any one or more if not all of these may be absolute or approximate to account for acceptable variations that may occur, such as those due to manufacturing or engineering tolerances or the like.

The phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. As used herein, the term “plurality” refers to two or more items or components. The terms “comprising,” “including,” “carrying,” “having,” “containing,” and “involving,” whether in the written description or the claims and the like, are open-ended terms, i.e., to mean “including but not limited to,” unless otherwise stated. Thus, the use of such terms is meant to encompass the items listed thereafter, and equivalents thereof, as well as additional items. The transitional phrases “consisting of” and “consisting essentially of,” are closed or semi-closed transitional phrases, respectively, with respect to any claims. Use of ordinal terms such as “first,” “second,” “third,” and the like in the claims to modify a claim element does not by itself connote any priority, precedence, or order of one claim element over another or the temporal order in which acts of a method are performed, but are used merely as labels to distinguish one claim element having a certain name from another element having a same name (but for use of the ordinal term) to distinguish claim elements.

Embodiments of the present disclosure are directed to methods and systems for enhancing operation of hydraulic fracturing equipment at a hydraulic fracturing wellsite. The methods and systems detailed herein may be executed on a controller which controls all equipment at the hydraulic fracturing wellsite and may provide various determinations, prompts, and/or requests in relation to hydraulic fracturing pumps and/or engines to provide power to the hydraulic fracturing pumps.

FIG. 1 is a top-down schematic view of a wellsite hydraulic fracturing system 100, according to an embodiment. The wellsite hydraulic fracturing system 100 may include a plurality of mobile power units 102 to drive electrical generators 104. The electrical generators 104 may provide electrical power to the wellsite hydraulic fracturing system 100. In other words, the electric generators 104 may provide electrical power to hydraulic fracturing equipment at the wellsite hydraulic fracturing system 100. In such examples, the mobile power units 102 may include an internal combustion engine 103. The internal combustion engine 103 may connect to a source of fuel. The internal combustion engine 103 may be a gas turbine engine (GTE) or a reciprocating-piston engine. In another example, other types of engines may be utilized to provide energy. In another embodiment, the electrical generators 104 may power the backside equipment 120.

In another example, the GTEs may be dual-fuel or bi-fuel. In other words, the GTE may be operable using two or more different types of fuel, such as natural gas and diesel fuel, or other types of fuel. A dual-fuel or bi-fuel GTE may be operable using a first type of fuel, a second type of fuel, and/or a combination of the first type of fuel and the second type of fuel. For example, the fuel may include gaseous fuels, such as, compressed natural gas (CNG), natural gas, field gas, pipeline gas, methane, propane, butane, and/or liquid fuels, such as, diesel fuel (e.g., #2 diesel), bio-diesel fuel, bio-fuel, alcohol, gasoline, gasohol, aviation fuel, and other fuels. The gaseous fuels may be supplied by CNG bulk vessels, a gas compressor, a liquid natural gas vaporizer, line gas, and/or well-gas produced natural gas. Other types and associated fuel supply sources are contemplated. The one or more internal combustion engines 103 may be operated to provide power or horse power to drive the transmission 136 connected to the electrical generators to provide electrical power to the hydraulic fracturing equipment at the wellsite hydraulic fracturing system 100.

The wellsite hydraulic fracturing system 100 may also include one or more hydraulic fracturing units 160. The hydraulic fracturing units 160 may include a plurality of mobile power units 106 to drive hydraulic fracturing pumps 108. The mobile power units 106 may include an internal combustion engine 107 (e.g., a GTE or reciprocating-piston engine), other engine, or power source. The hydraulic fracturing pumps 108 may be directly-driven turbine (DDT) hydraulic fracturing pumps. In such examples, the internal combustion engine 107 may connect to a DDT hydraulic fracturing pump via transmission 138 connected to a drive shaft, the drive shaft connected to an input flange of the DDT hydraulic fracturing pump. Other engine-to-pump connections may be utilized. In another embodiment, the mobile power units 106 may include auxiliary internal combustion engines, auxiliary electric generators, backup power sources, and/or some combination thereof.

In another example, the hydraulic fracturing pumps 108 may be positioned around a wellhead 110 and may discharge, at a high pressure, slurry to a manifold 144 such that the slurry may be provided to the wellhead 110 for a hydraulic fracturing stage, as will be understood by those skilled in the art. In such examples, each of the hydraulic fracturing pumps 108 may discharge the slurry through high-pressure discharge lines 109 to flow lines 111 on manifold 144. The flow lines 111 may connect to or combine at the manifold 144. The manifold 144 may provide the slurry to a manifold assembly 113. The manifold assembly 113 may provide the slurry to the one or more wellheads 110. After a hydraulic fracturing stage is complete, some portion of the slurry may return to a flowback manifold (not shown). From the flowback manifold, the slurry may flow to a flowback tank (not shown).

In an embodiment, the slurry may refer to a mixture of fluid (such as water), proppants, and chemical additives. The proppants may be small granules, for example, sand, ceramics, gravel, other particulates, and/or some combination thereof. Further, the granules may be coated in resin. As noted above, once fractures are introduced in reservoir rocks or formations and the slurry is drained or pumped back, the proppants may remain and “prop,” or keep open, the newly formed fractures, thus preventing the newly formed fractures from closing or, at least, reducing contracture of the newly formed fractures. Further, chemicals may be added to the slurry. For example, the chemicals may be thickening agents, gels, dilute acids, biocides, breakers, corrosion inhibitors, friction reducers, potassium chloride, oxygen scavengers, pH adjusting agents, scale inhibitors, and/or surfactants. Other chemical additives may be utilized.

The wellsite hydraulic fracturing system 100 may also include a blender unit 112, a hydration unit 114, a chemical additive unit 116, and a conveyor 118, one or more of which may referred to as backside equipment 120. In an embodiment, for a hydraulic fracturing stage, the blender unit 112 may provide an amount of slurry at a specified flow rate to the hydraulic fracturing pumps 108, the slurry to be discharged by the hydraulic fracturing pumps 108 to the wellhead 110 (as described above). The flow rate for slurry from the blender unit 112 may be determined by a sensor such as a flow meter (e.g., a blender flow rate meter 161). Further, the conveyor 118 may provide proppant to a mixer 122 of the blender unit 112. The conveyor 118 may include a conveyor belt, an auger, a chute (e.g., including a mechanism to allow passage of a specified amount of proppant), and/or other equipment to move or transfer proppant to the blender unit 112, as will be understood by those skilled in the art. Further still, the hydration unit 114 may provide a specified amount of fluid, from water tanks 115, and chemicals, from the chemical additive unit 116, to the mixer 122 of the blender unit 112. The chemical additive unit 116 may provide a specified amount and type of chemicals to hydration unit 114. The mixer 122 of the blender unit 112 may mix the fluid, proppant, and chemicals to create the slurry to be utilized by the hydraulic fracturing pumps 108. As noted above, the blender unit 112 may then pressurize and discharge the slurry from hose 142 to flow line 140 to the hydraulic fracturing pumps 108.

In another example, the wellsite hydraulic fracturing system 100 or a portion of the wellsite hydraulic fracturing system 100 may be mobile or portable. Such mobility may allow for the wellsite hydraulic fracturing system 100 to be assembled or disassembled quickly. For example, a majority of the hydraulic fracturing equipment may be included on trailers attached to vehicles or on the vehicles. When a wellsite starts hydraulic fracturing stages (e.g., hydraulic fracturing operations and/or jobs), the hydraulic fracturing equipment may be brought to the wellsite, assembled, and utilized and when the hydraulic fracturing stages are completed, the hydraulic fracturing equipment may be disassembled and transported to another wellsite. In such examples, data or hydraulic fracturing stage parameters may be retained by a supervisory controller 124 or another computing device.

The wellsite hydraulic fracturing system 100 may also include a control unit, a control center, a data van, a data center, a computing device, a controller, and/or a supervisory controller 124 to monitor and/or control operations of hydraulic fracturing equipment at the wellsite. In other words, the supervisory controller 124 or any of the other devices or systems noted above may be in signal communication with the hydraulic fracturing equipment. For example, the supervisory controller 124 may be in signal communication, to transmit and receive signals, with components, other controllers, and/or sensors included on or with the mobile power units 102 driving the electrical generators 104, the electrical generators 104, the internal combustion engines 103, the hydraulic fracturing units 160, the mobile power units 106 driving the hydraulic fracturing pumps 108, the hydraulic fracturing pumps 108, the internal combustion engines 107, the manifold 144, the wellhead 110, the flow line 111, the hose 142, the backside equipment 120, or some combination thereof. Further, other equipment may be included in the same location as the supervisory controller 124, such as a display or terminal, an input device, other computing devices, and/or other electronic devices.

As used herein, “signal communication” refers to electric communication such as hard wiring two components together or wireless communication, as will be understood by those skilled in the art. For example, wireless communication may be Wi-Fi®, Bluetooth®, ZigBee®, or forms of near field communications. In addition, signal communication may include one or more intermediate controllers or relays disposed between elements that are in signal communication with one another.

In another embodiment, the supervisory controller 124 may be in signal communication with a display, terminal and/or a computing device, as well as associated input devices. Further, the display may be included with a computing device. The computing device may include a user interface, the user interface to be displayed on the display. In such examples, the user interface may be a graphical user interface (GUI). In another example, the user interface may be an operating system. In such examples, the operating system may include various firmware, software, and/or drivers that allow a user to communicate or interface with, via input devices, the hardware of the computing device and, thus, with the supervisory controller 124. The supervisory controller 124 may provide data, a user interface, a GUI, and/or a window with various data points and interactive selections based on a pump profile, an engine profile, and/or a hydraulic fracturing unit profile. Such data may be provided via instructions stored in memory of the supervisory controller 124, the instructions to be executed by a processor of the supervisory controller 124. The computing device may include other peripherals or input devices, such as a mouse, a pointer device, a keyboard, a touchscreen, and/or other input devices. The supervisory controller 124 may communicate, send, or transmit prompts, requests, dashboards, or notifications to the display (e.g., through the computing device to the display). As used herein, “user” may refer to an operator, a single operator, a person, or any personnel at, or remote from, the wellsite hydraulic fracturing system 100. In another embodiment, a user may send data, for example, through data entry, via an input device, into a computing device associated with the display for a hydraulic fracturing stage profile, from the display to the supervisory controller 124. The user may send responses, for example, through user selection of a prompt, via the input device, or on the display, from the display to the supervisory controller 124.

In an embodiment, the supervisory controller 124 may be in signal communication with the backside equipment 120 to control the hydraulic fracturing stage parameters for a hydraulic fracturing stage. In other words, the supervisory controller 124 may communicate the hydraulic fracturing stage parameters to and/or control the backside equipment 120 for a current hydraulic fracturing stage. Further, the supervisory controller 124 may communicate with controllers of the backside equipment 120. For example, the supervisory controller 124 may transmit, to controller 150 the chemical additive unit 116, the amount and type of chemicals to be sent to the hydration unit 114 for the current hydraulic fracturing stage. The supervisory controller 124 may also transmit, through the signal communication, the amount of fluid, to the controller 148 of the hydration unit 114, to provide to the mixer 122 of the blender unit 112 for the current hydraulic fracturing stage. Further, the supervisory controller 124 may also transmit, through the signal communication, the amount and type of proppant, to the controller 152 of the conveyor 118, to provide to the mixer 122 of the blender unit 112 for the current hydraulic fracturing stage. Further still, the supervisory controller 124 may transmit, through the signal communication, to a controller 154 of the blender unit 112 the flow rate of the slurry from the blender unit 112 to a set of the hydraulic fracturing pumps 108 for the current hydraulic fracturing stage. The supervisory controller 124 may also be in signal communication with the hydraulic fracturing pumps 108 and/or a controller 146 of the hydraulic fracturing pumps 108 to control or transmit the flow rate (minimum and/or maximum flow rate) of the discharge of the slurry from the set of the hydraulic fracturing pumps 108, the maximum pressure of the slurry, and/or the pressure rating (e.g., a minimum and/or maximum pressure rate) of the slurry for the current hydraulic fracturing stage. Each of the one or more hydraulic fracturing unit controllers may include one or more alarms, alarm conditions, events, and/or event conditions to be communicated to the supervisory controller 124. For example, a controller 146 of a hydraulic fracturing pump may store conditions for when to generate an alarm and/or event and/or a history of prior generated alarms and/or events.

The supervisory controller 124 may also be in signal communication with various sensors, equipment, controllers and/or other components disposed around and on the hydraulic fracturing equipment at the wellsite hydraulic fracturing system 100. For example, the supervisory controller 124 may receive a measurement of pressure and flow rate of the slurry being delivered to the wellhead 110 from a wellhead pressure transducer 128, the pressure and flow rate of the slurry at a manifold pressure transducer 130, the pressure of the slurry at a hydraulic fracturing pump output pressure transducer 132, and/or data related to each of the hydraulic fracturing pumps 108 from a hydraulic fracturing pump profiler. The wellhead pressure transducer 128 may be disposed at the wellhead 110 to measure a pressure of the fluid at the wellhead 110. While the manifold pressure transducer 130 may be disposed at the end of the manifold 144 (as shown in FIG. 1 ), it will be understood by those skilled in the art, that the pressure within the manifold 144 may be substantially the same throughout the entire manifold 144 such that the manifold pressure transducer 130 may be disposed anywhere within the manifold 144 to provide a pressure of the fluid being delivered to the wellhead 110. The hydraulic fracturing pump output pressure transducer 132 may be disposed adjacent an output of one of the hydraulic fracturing pumps 108, which may be in fluid communication with the manifold 144 and thus, the fluid at the output of the hydraulic fracturing pumps 108 may be at substantially the same pressure as the fluid in the manifold 144 and the fluid being provided to the wellhead 110. Each of the hydraulic fracturing pumps 108 may include a hydraulic fracturing pump output pressure transducer 132 and the supervisory controller 124 may determine the fluid pressure provided to the wellhead 110 as an average of the fluid pressure measured by each of the hydraulic fracturing pump output pressure transducers 132.

One or more of the hydraulic fracturing units 160 may include a hydraulic fracturing pump profiler. The hydraulic fracturing pump profiler may be instructions stored in a memory, executable by a processor, in a controller 146. The hydraulic fracturing pump profiler may be a computing device or controller disposed on or connected to each of the hydraulic fracturing units 160. In another example, one controller or more may connect to more than one of the one or more hydraulic fracturing units 160. The hydraulic fracturing pump profiler may provide various data points related to each of the one or more hydraulic fracturing pumps 108 to the supervisory controller 124, for example, the hydraulic fracturing pump profiler may provide data including hydraulic fracturing pump characteristics (e.g., minimum flow rate, maximum flow rate, harmonization rate, and/or hydraulic fracturing pump condition). The hydraulic fracturing pump profiler may provide, to the supervisory controller 124, maintenance data associated with the one or more hydraulic fracturing pumps 108 and/or mobile power units 106 (e.g., health, maintenance schedules and/or histories associated with the hydraulic fracturing pumps 108, the internal combustion engine 107, and/or the transmission 138). The hydraulic fracturing pump profiler may provide, to the supervisory controller 124, operation data associated with the one or more hydraulic fracturing pumps 108 and/or mobile power units 106, for example, historical data associated with power or horse power, fluid pressures, fluid flow rates, etc., such examples being associated with operation of the hydraulic fracturing pumps 108 and mobile power units 106. The hydraulic fracturing pump profiler may provide, to the supervisory controller 124, data related to the transmissions 138, for example, hours of operation, health, efficiency, and/or installation age. The hydraulic fracturing pump profiler may provide, to the supervisory controller 124, data related to the internal combustion engines 107, for example, hours of operation, health, available power, and/or installation age. The hydraulic fracturing pump profiler may provide, to the supervisory controller 124, information related to the one or more hydraulic fracturing pumps 108, for example, hours of operation, plunger and/or stroke size, maximum speed, efficiency, health, and/or installation age. The hydraulic fracturing pump profiler may provide, to the supervisory controller 124, one or more of numerous alarm conditions and/or equipment alarm history, for example, life reduction events, pump cavitation events, pump pulsation events, and/or emergency shutdown events. The supervisory controller 124 may generate or obtain this data from a local controller for the internal combustion engines 107, engine sensors disposed on the internal combustion engines 107, a local controller for the transmissions 138, transmission sensors disposed on the transmissions 138, a local controller for the hydraulic fracturing pump 108, and/or pump sensors disposed on the hydraulic fracturing pumps 108.

In an embodiment, data, configuration, health ratings, and/or consumable data associated with any of the components or equipment included on the hydraulic fracturing unit 160 may be considered hydraulic fracturing unit parameters. The components or equipment may refer to the hydraulic fracturing pumps 108, the internal combustion engine 107, the transmission 138, a fluid end, and/or any other equipment included on or with or disposed on the hydraulic fracturing unit 160.

FIGS. 2A and 2B are block diagrams of a supervisory controller 124 connected to backside equipment 120, hydraulic fracturing pumps 108, a display 206, and a computing device 208, according to an embodiment. The supervisory controller 124 may include a machine-readable storage medium (for example, memory 202) and processor 204. As used herein, a “machine-readable storage medium” may be any electronic, magnetic, optical, or other physical storage apparatus to contain or store information such as executable instructions, data, and the like. For example, any machine-readable storage medium described herein may be any of random access memory (RAM), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state drive, any type of storage disc, and the like, or a combination thereof. As noted, the memory 202 may store or include instructions executable by the processor 204. As used herein, a “processor” may include, for example one processor or multiple processors included in a single device or distributed across multiple computing devices. The processor 204 may be at least one of a central processing unit (CPU), a semiconductor-based microprocessor, a graphics processing unit (GPU), a field-programmable gate array (FPGA) to retrieve and execute instructions, a real time processor (RTP), other electronic circuitry suitable for the retrieval and execution of instructions stored on a machine-readable storage medium, or a combination thereof. The supervisory controller 124 may include instructions to build pump profiles or hydraulic fracturing unit profiles to monitor hydraulic fracturing units 160 and/or other hydraulic fracturing equipment and to determine characteristics, maintenance cycles, adjustments to ratings, health, and/or other factors associated with the hydraulic fracturing units 160 and/or other hydraulic fracturing equipment.

As noted, the supervisory controller 124 may be in signal communication with the backside equipment and the hydraulic fracturing units 160. The hydraulic fracturing units 160 may include large sets of data (e.g., operation data, maintenance data, and equipment data) related to the hydraulic fracturing units 160. The hydraulic fracturing units 160 may include various sensors, controllers, and/or other devices. The supervisory controller 124 may connect to each of the sensors, controllers, and/or other devices (for example, via a serial, RS422, REST, RESTful, Web Socket®, wirelessly, and/or wired interface) and include instructions, when executed by the processor, to obtain data from various sensors, controllers, and/or other devices. The hydraulic fracturing units 160 may include a controller 146 and/or sensors 162. Further, the supervisory controller 124 may obtain data from the one or more hydraulic fracturing unit 160 controller 146 and/or sensor 162 or from other components, devices, or equipment included on or with the one or more hydraulic fracturing units 160, such as, a set of maintenance data, a set of operation data, a set of equipment health ratings, a set of equipment configurations, and a set of equipment event and alarm histories. The maintenance data may include the number of hours until next required or suggested engine maintenance, the number of hours until the next required or suggested transmission maintenance, an oil change log, pump valve and seat (V&S) hours, packing hours, total pump strokes, average V&S hours, and average packing hours. The operation data may include the maximum hydraulic power produced and/or utilized during a previous hydraulic fracturing stage, a minimum hydraulic power utilized, an average hydraulic power, a maximum pressure produced, a maximum flow produced, a maximum pump speed, and/or a user override register. The pump speed may be represented or indicated by the rotations per minute (RPM) of the pump. The hydraulic power may be represented or indicated by hydraulic horse power (HHP). The equipment health ratings may include the engine health, engine power rating based on engine health, transmission health, transmission deration based on health, pump health, and/or pump deration based on health. The engine power may be represented or indicated by horse power (HP). The equipment configurations may include an engine model, engine serial number, transmission model, transmission serial number, pump model, pump serial number, fluid end model, and/or fluid end serial number. The equipment event and alarm histories may include life reduction event counter total, life reduction event for current week, pump cavitation event counter total, pump cavitation event counter for current week, pump pulsation event counter total, pump pulsation event counter for current week, emergency shutdown counter total, and/or emergency shutdown counter for current week. In another example, the supervisory controller 124 may obtain the locations and/or positions of the hydraulic fracturing units 160, for example, the location or position of a particular hydraulic fracturing unit in relation to the other hydraulic fracturing units, which may be denoted by a number, a letter, coordinates, and/or other information indicating a position and/or location of equipment. Other data related to the hydraulic fracturing units 160 may be included and/or may be obtained by the supervisory controller 124.

As noted, the hydraulic fracturing pumps 108 may include a controller 164 and/or sensors 166. The supervisory controller 124 may obtain data from a hydraulic fracturing pump 108 controller 164 and/or sensors 166 or from other components, devices, and/or equipment included on or with the hydraulic fracturing unit's 160, such as pump information, including the number of hours of use of the pump, the pump's plunger size, the pump's stroke size, the pump's maximum speed, the pump's health efficiency, consumables age (e.g., V&S hours and/or age), and an age of the pump. Further, the supervisory controller 124 may continuously or periodically obtain, retrieve, or request data from the hydraulic fracturing pump's 108 controller 164 and/or sensors 166. Further still, the supervisory controller 124 may continuously, substantially continuously, or periodically obtain, retrieve, or request specific data from the hydraulic fracturing pump's 108 controller 164 and/or sensors 166 (e.g., hours per use, health efficiency, pressure at the hydraulic fracturing pump's 108 output, flow rate, speed, or other information that may change periodically or frequently).

In another embodiment, the supervisory controller 124 and/or the hydraulic fracturing pump's 108 controller 164 may include instructions to generate and transmit events and/or alarms of varying severity (e.g., low severity, allowing for continued operation, to critical severity, which may cause immediate shutdown of equipment). For example, a threshold may be set for various factors associated with the hydraulic fracturing pump 108, for example, pressure at the hydraulic fracturing pump's 108 output, flow rate, speed, consumables age, and/or other operating factors. The supervisory controller 124 may monitor the data associated with a threshold from the hydraulic fracturing pump's 108 controller 164 and/or sensors 166. If the threshold is met or exceeded, then the supervisory controller 124 and/or controller 164 may prevent use of, prevent further use of, stop, or send a stop signal to the hydraulic fracturing pump 108. In another embodiment, the supervisory controller 124 and/or controller 164 may record the event and prevent the use of the pump in a next hydraulic fracturing stage until maintenance is performed on hydraulic fracturing pump 108. In such embodiments, the threshold may be a value that operating parameters are not to be greater than, greater than or equal to, less than, or less than or equal to.

The hydraulic fracturing unit's 160 transmission 138 may include a controller 168 and/or sensors 170. The supervisory controller 124 may obtain data from the transmission's 138 controller 168 and/or sensors 170 or from other components, devices, or equipment included on or with the hydraulic fracturing unit's 160, such as transmission information, number of hours of use of the transmission, the transmission's installation age, the transmission's efficiency health, transmission fluid level, transmission fluid age, transmission fluid grade or health, and/or other data related to the transmission 138. The supervisory controller 124 or controller 168 may include a threshold or conditions and/or may include an option to set a threshold or conditions to trigger events and/or alarms of varying severity (e.g., low severity, allowing for continued operation, to critical severity, which may cause immediate shutdown of equipment). For example, the supervisory controller 124 or controller 168 may include a threshold for transmission fluid level. If the transmission fluid falls below or is at a certain level, either specified or preset, then the supervisory controller 124 or controller 168 may generate an alarm. Further, the supervisory controller 124 or controller 168 may inhibit upshift out of neutral, thus preventing damage to the transmission 138. The supervisory controller 124 or controller 168 may prevent upshift out of neutral until manual intervention or maintenance is performed. The threshold may be preset or set in the supervisory controller 124. In another example, the supervisory controller 124 may determine the threshold based on transmission data.

As noted, the internal combustion engine 107 may include a controller 172 and/or sensors 174. The supervisory controller 124 may obtain data from the internal combustion engine's 107 controller 172 and/or sensors 174 or from other components, devices, or equipment included on or with the hydraulic fracturing unit's 160, such as engine information, including the number of hours of use of the engine, the engine's available power, the engine's installation age, the engine's efficiency health, consumables levels, consumables age, and/or other information related to the engine. The supervisory controller 124 or controller 172 may include a threshold or conditions and/or may include an option to set a threshold or conditions to trigger events and/or alarms of varying severity (e.g., low severity, allowing for continued operation, to critical severity, which may cause immediate shutdown of equipment). For example, the supervisory controller 124 or controller 172 may include a threshold for consumable level, consumable age, hours of use, and/or other factors. If a measurement falls below, exceeds, or is at a certain level, either specified, preset, or determined by the supervisory controller 124 based on engine data, then the supervisory controller 124 or controller 172 may generate an alarm. Further, the supervisory controller 124 or controller 172 may prevent further use of the internal combustion engine 107 to ensure that no damage occurs to the internal combustion engine 107. The supervisory controller 124 or controller 172 may prevent start-up of the internal combustion engine 107 until manual intervention or maintenance is performed.

As noted above, the supervisory controller 124 may be in signal communication with the backside equipment 120. In such examples, the connection between the controller 124 and backside equipment 120 may be a representational state transfer (REST or RESTful) interface, a WebSocket® interface, or some other transmission control protocol (TCP) or QUIC based interface. In such examples, the current hydraulic fracturing stage parameters may be sent from the controller 124 to the backside equipment 120 over hypertext transfer protocol (HTTP), hypertext transfer protocol secure (HTTPS), or other protocol. The supervisory controller 124 may also obtain data and build profiles relating to associated backside equipment 120.

The supervisory controller 124 may include instructions stored in the memory 202, when executed by the processor 204, to build, determine, or create a hydraulic fracturing unit profile or pump profile. The supervisory controller 124 may obtain the data noted above and create and/or format the data into a format suitable for the display 206. In such examples, in response to reception of the data described above, the processor 204 of the supervisory controller 124 may execute instructions to build, determine, and/or create a health assessment. The health assessment may be based on the equipment health ratings. The health assessment may also be based on all the data obtained by the supervisory controller 124, for example, hours used, age of equipment, consumable levels, consumable age, and/or other factors as described herein. The health assessment may be stored as a value or indicator. The value or indicator may correspond to a color to transmit or send to the display 206. For example, a poor health assessment of a hydraulic fracturing unit may be determined and stored in the memory 202 of the supervisory controller 124 as, for example, a “1”. Other values and indicators may be utilized, as will be understood by those skilled in the art. The supervisory controller 124 may package or transmit the health assessment with the hydraulic fracturing profile or pump profile. The health assessment may then be presented to a user, via the display 206, as a color, for example, red for the poor health assessment. Green may represent a good health assessment, and yellow may represent a state in between good and poor. For example, the supervisory controller 124 may recommend or automatically set a maintenance date between a week and two weeks for a hydraulic fracturing unit with a yellow health assessment may.

The supervisory controller 124 may include instructions stored in the memory 202, when executed by the processor 204, to present a GUI or dashboard to the display 206, a terminal, a smartphone, and/or a tablet. The GUI or dashboard may include a selectable list of the hydraulic fracturing units 160 or selectable tabs, each tab associated with a hydraulic fracturing unit 160. In another embodiment, the GUI or dashboard may include a representation of the equipment at the wellsite (e.g., boxes or drawings for equipment, such as for the hydraulic fracturing units 160). In such an embodiment, each representation may be selectable. The user may select one of the hydraulic fracturing units 160. In response to a selection of one of the one or more hydraulic fracturing units 160, the GUI or dashboard may present the hydraulic fracturing unit profile or the pump profile. The hydraulic fracturing unit profile or pump profile may be presented on the display 206 as a series of tabs. When a user selects a tab, the GUI or dashboard may present the relevant data. For example, one tab may be an internal combustion engine tab (indicated by text, such as “Engine”). When a user clicks the internal combustion engine tab, the internal combustion engine data may be presented. The GUI or dashboard may include a main tab, home tab, or home page for each hydraulic fracturing unit profiles or pump profiles. The main tab, home tab, or home page may include the health assessment. When the health assessment is poor or includes an indication that user intervention may be needed and the user hovers over or selects the health assessment, a list of the issues causing or potentially causing the state of the health assessment may be listed. Such a list may include potential corrective actions that may be performed. At such a point, the user may take corrective action. After a corrective action is taken, the supervisory controller 124 may determine what time the corrective action was taken and what type of corrective action occurred. The supervisory controller 124 may update the GUI or dashboard for the respective hydraulic fracturing unit 160. The supervisory controller 124 may store the taken corrective action, with a timestamp, and present the corrective action in the GUI or dashboard in a section related to an associated hydraulic fracturing unit.

The supervisory controller 124 may include instructions stored in the memory 202, when executed by the processor 204, to prompt or notify a user in response to an event. In an embodiment, an event may be a life reduction event, pump cavitation event, pump pulsation event, and/or emergency shutdown. While such events, as well as other events, may include an associated corrective action, the events may not require a corrective action. The supervisory controller 124 may, for example, derate a pump based one or more such events or data obtained or determined, e.g., health ratings, health assessment, pump information/data, and/or other data or information described herein. In another embodiment, the supervisory controller 124 may determine a level to derate the pump to. In such cases, the supervisory controller may send a prompt to a user to accept such an action or may automatically derate the pump. In another embodiment, the supervisory controller 124 may adjust factors associated the hydraulic fracturing units 160 based on such events. For example, when an event occurs (e.g., pump cavitation, pump pulsation, etc.), the supervisory controller 124 may adjust factors associated with the respective hydraulic fracturing unit 160 (e.g., lowering a pumps maximum speed, pressure, or flow rate, or lowering max power output by an engine, etc.).

The supervisory controller 124 may include instructions stored in the memory 202, when executed by the processor 204, to determine a hydraulic fracturing pumps 108 flow or maximum flow based on the hydraulic fracturing unit's profile or pump profile. The supervisory controller 124 may utilize the stroke length (SL), the plunger size or diameter (PD), number of cylinders (NC), and maximum speed to accurately calculate maximum flow rate of a hydraulic fracturing pump 108. The following formula may be utilized to determine the displacement per revolution (GPR) of the hydraulic fracturing pump 108:

$\frac{PD^{2} \times \text{.7854} \times {SL} \times {NC}}{231} = {GPR}$

Once the GPR is determined, the supervisory controller 124 may convert GPR to gallons per minute (GPM) by multiplying GPR by pump speed. The pump speed may be represented or indicated by a pump's RPM. The supervisory controller 124 may further convert GPM to barrels per minute (BPM). Further, the supervisory controller 124 may determine the maximum pressure of the hydraulic fracturing pump 108 using the maximum rod load (RL) and PD. The following equation may be utilized to determine the maximum pressure of the hydraulic fracturing pump 108:

$\frac{RL}{PD^{2} \times \text{.7854}} = {PSI}$

Other aspects of or factors associated with the hydraulic fracturing pumps 108 or the hydraulic fracturing unit 160 may be determined based on data in the hydraulic fracturing unit's profile or pump profile, such as, power utilization, power output, or other aspects.

The supervisory controller 124 may include instructions stored in the memory 202, when executed by the processor 204, to obtain or determine a life of the consumables in the one or more hydraulic fracturing units 160. The supervisory controller 124 may determine or calculate an expected or average life of a consumable based on the hydraulic fracturing unit profile or pump profile. Further the supervisory controller 124 may check the consumables continuously, substantially continuously, periodically, or at regular intervals. If the consumables are lower than an expected or average level and/or older than an expected or average age, the supervisory controller 124 may prompt the user. Further, if the consumables are lower than an expected or average level at a time period less than the expected or average life of the consumables, then the prompt may include a warning that the hydraulic fracturing unit 160 may be experiencing an issue or wear. The prompt may include a notice that a hydraulic fracturing unit 160 may not be utilized until maintenance is performed and the supervisory controller 124 may prevent such use until the maintenance is performed. For example, such a prompt may indicate hydraulic fracturing pump 108 operation issues, internal combustion engine 107 issues, transmission 138 issues, suction line issues, and/or fluid end wear. Consumables may refer to any fluid or solid consumed by the hydraulic fracturing units 160 during the hydraulic fracturing stage or process. A consumable may also be diesel fuel (e.g., #2 diesel), bio-diesel fuel, bio-fuel, alcohol, gasoline, gasohol, aviation fuel, other fuels, fluids, water, chemicals, or other substances as will be understood by those skilled in the art. Consumables may also refer to any components that are periodically replaced or wear out, e.g., V&S.

The supervisory controller 124 may include instructions stored in the memory 202, when executed by the processor 204, to determine which hydraulic fracturing units 160 to utilize in or for a hydraulic fracturing stage or operation. The supervisory controller 124 may determine which hydraulic fracturing units 160 to use based on the hydraulic unit profile and/or the pump profile. The supervisory controller 124 may determine that a specific hydraulic fracturing unit 160 may not be utilized for a particular hydraulic fracturing stage or operation based on the maximum power of the specific hydraulic fracturing unit being less than required for the hydraulic fracturing stage or operation, the maximum flow rate of the specific hydraulic fracturing unit being less than required for the hydraulic fracturing stage or operation, the level and/or age of consumables within the specific hydraulic fracturing unit, upcoming maintenance for the specific hydraulic fracturing unit, health ratings and/or assessments, other data and/or determinations associated with the hydraulic fracturing unit as described herein, and/or some combination thereof. For example, a specific hydraulic fracturing unit with an insufficient amount of a consumable (e.g., diesel) for a desired length of time of a hydraulic fracturing stage or operation may not be selected for such a hydraulic fracturing stage or operation. In another example, a specific hydraulic fracturing unit with a low or poor health rating or assessment may be taken offline for maintenance, rather than to be utilized in the hydraulic fracturing stage or operation. Other factors may be considered in various other examples.

FIGS. 3A and 3B are flowcharts of example method 300 of utilizing and amending hydraulic fracturing stage profiles, according to an embodiment. The method is detailed with reference to the wellsite hydraulic fracturing system 100 and supervisory controller 124. Unless otherwise specified, the actions of method 300 may be completed within the supervisory controller 124. Specifically, method 300 may be included in one or more programs, protocols, or instructions loaded into the memory 202 of the supervisory controller 124 and executed on the processor 204. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks may be combined in any order and/or in parallel to implement the methods.

At block 302, the supervisory controller 124 may determine if a hydraulic fracturing pump's 108 controller 164 is available. The hydraulic fracturing pump's 108 controller 164 may be considered available when a hydraulic fracturing unit 160 is brought, driven, delivered, started, and/or initiated at a wellsite hydraulic fracturing system 100. In another embodiment, the hydraulic fracturing pump's 108 controller 164 may be considered available when a hydraulic fracturing unit 160 is brought online and the hydraulic fracturing pump's 108 controller 164 connected to the supervisory controller 124, either via a hard wired connection or wireless connection. The supervisory controller 124 may wait until at least one hydraulic fracturing pump's 108 controller 164 is available prior to initiating building or determining a hydraulic fracturing unit profile or pump profile.

At block 304, once the supervisory controller 124 has connected to one or more hydraulic fracturing pumps' 108 controllers 164, the supervisory controller 124 may obtain data from the controller 164. The supervisory controller 124 may obtain pump assembly data for each hydraulic fracturing pump 108 at the wellsite hydraulic fracturing system 100. The pump assembly data may include a pump's plunger size, a pump's stroke size, and/or a pump's maximum speed. Other information, such as pump curves, pump models, pump serial numbers, pump placement, and/or other pump assembly characteristics may be obtained by the supervisory controller 124.

At block 306, the supervisory controller 124 may, after, before, or during the obtaining of pump assembly data, obtain pump maintenance data. The pump maintenance data may include the total number of hours a hydraulic fracturing pump 108 has been in use or the age of the hydraulic fracturing pump, a number of hours the hydraulic fracturing pump 108 has been in use since the last maintenance operation, the type of the last maintenance operation, and/or the time until the next scheduled, expected, and/or typical maintenance operation. In another embodiment, the supervisory controller 124 may obtain or receive, rather than the time until the next scheduled, expected, and/or typical maintenance operation, a pump manufacturers recommended time frame or period for maintenance.

At block 308, the supervisory controller 124 may obtain pump event and/or alarm history. The pump event and/or alarm history may include life reduction event counter total, life reduction event for the current week, month, and/or year, pump cavitation event counter total, pump cavitation event counter for the current week, month, and/or year, pump pulsation event counter total, pump pulsation event counter for the current week, month, and/or year, emergency shutdown counter total, and/or emergency shutdown counter for the current week, month, and/or year. In another embodiment, the supervisory controller 124 may determine and/or generate events and/or alarms based on data obtained from the hydraulic fracturing pump's 108 controller 164.

At block 310, the supervisory controller 124 may determine a hydraulic fracturing pump's 108 maintenance cycle. The supervisory controller 124 may determine such a cycle based on the pump maintenance data, the pump event and/or alarm history, and/or the pump assembly data. For example, the supervisory controller 124 may schedule a sooner-than-typical maintenance operation for a hydraulic fracturing pump 108 that experiences a high amount of cavitation or pulsation events, but has been in operation for a short period of time since a last maintenance operation. Based on various other conditions and hydraulic fracturing pump 108 characteristics, events, and alarms, the supervisory controller 124 may set a maintenance date.

At block 312, the supervisory controller 124 may determine various characteristics of the hydraulic fracturing pump 108 based on pump assembly data. For example, the supervisory controller 124 may determine a maximum flow rate of the hydraulic fracturing pump 108 based on the pump assembly data and/or other data or information described herein. In another embodiment the supervisory controller 124 may determine the maximum pressure and the maximum speed of the hydraulic fracturing pump 108 based on the pump assembly data. The determinations may further be based on pump maintenance data and/or pump event and/or alarm history. For example, the supervisory controller 124 may determine whether to derate a hydraulic fracturing pump 108 based on the pump assembly data, the pump maintenance data, and/or the pump event and/or alarm history. Such an operation (e.g., derating a pump) may alter the maximum speed, maximum pressure, and/or maximum flow rate of the hydraulic fracturing pump 108.

At block 314, the supervisory controller 124 may determine if an internal combustion engine's 107 controller 172 is available. The internal combustion engine's 107 controller 172 may be considered available when a hydraulic fracturing unit 160 is brought, driven, delivered, started, and/or initiated at a wellsite hydraulic fracturing system 100. In another embodiment, the internal combustion engine's 107 controller 172 may be considered available when a hydraulic fracturing unit 160 is brought online and the internal combustion engine's 107 controller 172 connected to the supervisory controller 124, either via a hard wired connection or wireless connection. The supervisory controller 124 may wait until at least one internal combustion engine's 107 controller 172 is available prior to initiating building or determining a hydraulic fracturing unit profile or pump profile.

At block 316, once the supervisory controller 124 has connected to one or more internal combustion engines' 107 controllers 172, the supervisory controller 124 may obtain data from the controller 172. The supervisory controller 124 may obtain engine assembly data for each internal combustion engine 108 at the wellsite hydraulic fracturing system 100. The engine assembly data may include a type of engine (e.g., internal combustion engine), power output and/or fuel type. Other information, such as engine model, engine serial numbers, engine placement, and/or other engine assembly characteristics may be obtained by the supervisory controller 124.

At block 318, the supervisory controller 124 may, after, before, or during the obtaining of engine assembly data, obtain engine maintenance data. The engine maintenance data may include the total number of hours an internal combustion engine 107 has been in use or the age of the internal combustion engine 107, a number of hours the internal combustion engine 107 has been in use since the last maintenance operation, the type of the last maintenance operation, the time until the next scheduled, expected, and/or typical maintenance operation, the level of fluids utilized in the internal combustion engine 107, the typical and/or optimal amount of the fluids to be used in the internal combustion engine 107, and/or the typical and/or optimal type of fluid to be used in the internal combustion engine 107. In another embodiment, the supervisory controller 124 may obtain or receive, rather than the time until the next scheduled, expected, and/or typical maintenance operation, an engine manufacturers recommended time frame or period for maintenance.

At block 320, the supervisory controller 124 may obtain pump event and/or alarm history. The pump event and/or alarm history may include life reduction event counter total, life reduction event for the current week, month, and/or year, emergency shutdown counter total, emergency shutdown counter for the current week, month, and/or year, missed scheduled maintenance, low or critically low consumables, and/or other events related to or associated with the internal combustion engine 107. In another embodiment, the supervisory controller 124 may determine and/or generate events and/or alarms based on data obtained from the internal combustion engine's 108 controller 172.

At block 322, the supervisory controller 124 may determine an average or expected life of consumables utilized in the internal combustion engine 107. The supervisory controller 124 may determine the average or expected life of a particular consumable based on engine assembly data and/or engine maintenance data. For example, for a particular liquid, the supervisory controller may determine the average or expected life based on the amount or level of the consumable in the internal combustion engine 107, the amount or level indicated by the manufacturer (which may be included in the engine assembly data), and/or the amount or level of the consumable in the engine following maintenance associated with the consumable.

In another embodiment, the supervisory controller 124 may determine an average or expected life of consumables utilized by the hydraulic fracturing pumps 108. The supervisory controller 124 may determine the average or expected life of a particular consumable based on pump assembly data and/or pump maintenance data. For example, for a component of the hydraulic fracturing pumps 108, the supervisory controller may determine the average or expected life based on prior maintenance time periods for the component and/or the average or expected life indicated by the manufacturer (which may be included in pump assembly data).

At block 324, the supervisory controller 124 may determine an internal combustion engine's 107 maintenance cycle. The supervisory controller 124 may determine such a cycle based on the engine maintenance data, the engine event and/or alarm history, and/or the engine assembly data. For example, the supervisory controller 124 may schedule a sooner than typical maintenance operation for an internal combustion engine's 107 that experiences a high amount of emergency shutdowns, but has been in operation for a short period of time since a last maintenance operation. Based on various other conditions and internal combustion engine 107 characteristics, events, and alarms, the supervisory controller 124 may set a maintenance date

At block 326, the supervisory controller 124 may determine various characteristics of the internal combustion engine 107 based on engine assembly data and/or engine maintenance data. For example, the supervisory controller 124 may determine a maximum power output of the internal combustion engine 107 based on the engine assembly data, engine maintenance data, health assessment, health rating, and/or other data.

In another embodiment, the data from the internal combustion engine's 107 controller 172 may be obtained at the same time or substantially the same time data is obtained from the hydraulic fracturing pump's controller 164. Data may be obtained sequentially, for example, from the hydraulic fracturing pumps 108 and then the internal combustion engine 107, or vice versa. Further, data from a transmission and/or fluid end may be obtained. Various factors and characteristics of the other equipment may be determined, as described herein. For example, transmission fluid level and maintenance may be monitored and determined.

After the average or expected life of the consumables utilized in the internal combustion engine 107 are determined, at block 328, the supervisory controller 124 may continue to monitor the consumables over time. For example, the supervisory controller 124 may continuously or periodically obtain or gather data associated with the consumables (e.g., current level, health, and/or time since last maintenance).

After an update to consumable related data, at block 330, the supervisory controller 124 may determine whether the consumables are low. For example, is the amount of consumables in the internal combustion engine 107 at a level that may cause damage or that may be insufficient to operate the internal combustion engine 107 for a period of time, for example, the time to finish a hydraulic fracturing stage.

If the consumables are not low, the supervisory controller 124 may continue to monitor the consumables. If the consumables are low, at block 332, the supervisory controller 124 may determine whether the consumable is low or has failed sooner than expected. For example, the supervisory controller 124 may determine whether the consumable has failed at a time less than the average or expected life. If the consumables are failing within the average or expected life, then the supervisory controller 124 may determine whether to perform maintenance. If the consumable has filed or is low at a time less the average or expected, at block 334, the supervisory controller 124 may determine the number of times that the consumables have failed in a time less than the average. In an embodiment, a threshold may be set to determine whether the consumable failure may indicate equipment failure. For example, if a consumable is utilized in a shorter than the average or expected life, then such repeated failure may indicate equipment failures, such as a leak. At block 338, if the number is greater than the threshold, the supervisory controller 124 may transmit a prompt, notification, and/or alarm.

At block 340, the supervisory controller 124 may determine whether maintenance is to be performed. For example, the consumable may be low, but not low enough to necessitate maintenance. If maintenance is not to be performed, the supervisory controller 124, at block 342, may determine whether to derate the pump. For example, if the consumables are at a specific level, the power output or maximum power output may be altered. In such an example, the supervisory controller may derate the hydraulic fracturing pump 108, at least until more consumable is added or maintained (e.g., removing old consumable and adding new consumable). If the supervisory controller 124 determines that the hydraulic fracturing pump 108 should be derated, the supervisory controller 124 may, at block 344, derate the pump or lower the capability (e.g., maximum pressure, maximum flow, and/or maximum speed of the hydraulic fracturing pump 108.

After the various characteristics and/or data related to the internal combustion engine 107 and/or hydraulic fracturing pump 108 are obtained and/or determined, at block 346, the supervisory controller 124 may determine whether the internal combustion engine 107 and/or hydraulic fracturing pump 108 require maintenance, based on the data gathered and determined. If the internal combustion engine 107 and/or hydraulic fracturing pump 108 are to receive maintenance, at block 348, the supervisory controller 124 may take the internal combustion engine 107 and/or hydraulic fracturing pump 108 offline, as in not available for use, or shut-off. Once the internal combustion engine 107 and/or hydraulic fracturing pump 108 are taken offline, at block 350, the supervisory controller 124 may transmit a prompt, notification, and/or alarm for maintenance to be performed. At block 352, the supervisory controller 124 may determine whether maintenance has been performed. The supervisory controller 124 may prevent the use of equipment until the maintenance has been performed. The supervisory controller 124 may obtain data from the internal combustion engine 107 and/or hydraulic fracturing pump 108 to determine whether the maintenance has been performed. In another embodiment, a user may indicate when the maintenance has been performed. After the maintenance has been performed, at block 354, the internal combustion engine 107 and/or hydraulic fracturing pump 108 may be brought back online, as in made available for use, or restarted.

At block 356, after all data in relation to the internal combustion engine 107 and/or hydraulic fracturing pump 108 has be obtained and/or determined, the supervisory controller may determine a rating or health rating for internal combustion engine 107 and/or hydraulic fracturing pump 108. A rating or health rating for other equipment included on the hydraulic fracturing unit 160 or elsewhere at the wellsite hydraulic fracturing system may be determined. Once the rating or health rating has been determined, the supervisory controller 358 may build a health profile, pump profile, and/or hydraulic fracturing unit profile for the internal combustion engine 107, hydraulic fracturing pump 108, and/or other equipment as described herein. The health profile, pump profile, and/or hydraulic fracturing unit profile may include the various data points, static and/or real-time, associated with the internal combustion engine 107 and/or hydraulic fracturing pump 108. The supervisory controller 124 may, at block 359, then determine which hydraulic fracturing units 160 to utilize in a hydraulic fracturing stage or operation based on the health profile, pump profile, and/or hydraulic fracturing unit profile.

At block 360, the supervisory controller 124 may determine whether to derate the hydraulic fracturing pump 108 based on the health profile. If the supervisory controller 124 determines that the hydraulic fracturing pump 108 should be derated, at block 362, the supervisory controller 124 may derate the hydraulic fracturing pump 108. The supervisory controller 124, at block 364, may then continuously or periodically check for data updates related to the internal combustion engine 107 and/or hydraulic fracturing pump 108. If an update is available, the supervisory controller 124 may determine an updated rating and update the health profile.

FIG. 4 is a block diagram of a wellsite hydraulic fracturing pumper system 400, according to an example. In an example, the controller or supervisory controller may be included in a data van 434. In such examples, the data van 434 may be separated into a control network 438 and business network 436. In another example, the control network 434 may include the controller, as well as user displays (e.g., a user or operator terminal 414). In such examples, the controller may include various electronic components. For example, the controller may include a switch (e.g., an Ethernet switch 402) to connect to the backside equipment 404 or backside equipment 404 controllers (e.g., via an interface 405 such as a REST, RESTful, or WebSocket® interface) and one or more hydraulic fracturing units 406 or the one or more hydraulic fracturing unit 406 controllers to an application delivery controller 408. In such examples, the application delivery controller 408 may connect to a server and backup or mirrored server (e.g., two connected and/or mirrored application servers 410) via another switch 412. In such examples, the controller may be considered the Ethernet switch 402, the application delivery controller 408, the switch 412, and the application servers 410. In another example, the controller may be in signal communication with user or operator terminals 414. In another example, the controller may connect to a wireless access point 416 or wireless router. In such examples, a user may connect to the controller via wireless signals. Further the user may connect to the controller via a smartphone 418 or tablet 420. In another example, a hydraulic fracturing pump interface 422, disposed on a controller or component of each of the hydraulic fracturing units 406, may be in direct electrical communication with an intermediate interface 424. The hydraulic fracturing pump interface 422 may be a serial interface (e.g., a RS422 interface). In another example, the hydraulic fracturing pump interface 422 may be a wireless interface. For example, the hydraulic fracturing pump interface 422 may send data, via a wireless network, to the intermediate interface 424. The intermediate interface 424 may be in direct electrical communication or wireless communication with the controller (e.g., through the Ethernet switch 402). In another example, the controller may connect to a controller or controllers for other components of the hydraulic fracturing units 406.

As noted, the data van 434 may include a business network 436 or business unit. The business network 436 may include a computing device 426 to store the hydraulic fracturing unit profile or pump profile, as well as other wellsite data and analytics. The computing device 426 may be in signal communication with the controller. The computing device 426 may be a server. In another example, the computing device 426 may be an edge server. In a further example, the computing device 426 may connect to a switch 428 to send, through an internet connection 430, data and/or analytics of the wellsite to a data center 432 for further analysis. Further, the hydraulic fracturing units 406 and backside equipment 404 may connect, through the internet connection 430, to the data center 432, thus providing real time data to the data center 432.

A processor executing instructions stored in memory of a supervisory controller or other computing device may build, determine, or create a hydraulic fracturing unit profile or pump profile. The supervisory controller may, for each pump profile, include, generate, or determine one or more corresponding or associated displays, pages, or GUIs. The pump profile may include a first GUI 500, as illustrated in FIG. 5 . The first GUI 500 may include real-time data, diagnostics, and actions taken regarding each hydraulic fracturing pump at a wellsite. The first GUI 500 may include a pump identification number 502, as multiple pump profiles may be built for one or more hydraulic fracturing pumps at a wellsite. The pump identification number 502 as illustrated in FIG. 5 may be represented by a number, letter, or other type of tag. The pump identification number 502 may indicate that the pump profile 500 corresponds to a particular hydraulic fracturing pump.

Real-time data associated with a particular hydraulic fracturing pump may be updated continuously or periodically. The first GUI 500 may include an actual BPM and/or set point BPM section 504. The supervisory controller and/or a user may set the BPM or determine a set point or limit for the BPM of a pump, for example, based on events and other characteristics of a pump. The supervisory controller may limit the BPM of a pump, preventing the pump from operating past such a limit. The first GUI 500 may also include other real-time operating data, with or without set limits, for example, the discharge pressure 506, suction pressure 508, vibration 511 (e.g., inches per second). The first GUI 500 may include various sections displaying different values for different characteristics (real-time operating data or static data) of the hydraulic fracturing pump, for example, turbine and/or engine data 514, 516, pump component data 510, and/or gearbox data 512. Such sections may illustrate current life of consumables associated with the hydraulic fracturing pump. If a consumable reaches a limit indicating a time for maintenance or replacement, the supervisory controller may generate an event and derate the hydraulic fracturing pump or prevent use of the hydraulic fracturing pump. The first GUI 500 may include such events and other events or actions taken or to be taken. For example, if a hydraulic fracturing pump experiences a certain event, for example, cavitation, the supervisory controller may determine that the hydraulic fracturing pump is to be derated (see 518, 522) and may automatically perform such an action. The supervisory controller may further prompt a user to take action or intervene 520 based on an event, e.g., high vibration and/or oil temperature above a limit. The first GUI 500 may also display real-time pump vibrations 524 and/or pump RPM 526 over time. The first GUI 500 may additionally include an idle button 528 and/or a stop button 530. Selecting the idle button 528 during non-operation may cause the associated hydraulic fracturing pump to enter an idle state. Selecting the stop button 530 during operation or idle may cause the associated hydraulic fracturing pump to enter a stop state or cease operation.

The supervisory controller may, for each pump profile, include, generate, or determine one or more corresponding or associated displays, pages, or GUIs. The pump profile may include a second GUI 600, as illustrated in FIG. 6 . The second GUI 600 may include data similar to the first GUI 500, such as a pump identification number 602, an actual BPM and/or set point BPM section 604, discharge pressure 606, suction pressure 608, and/or vibration 610. The second GUI 600 may include configuration data 612 or assembly data of a hydraulic fracturing pump. Configuration data 612 may include the make, model, serial number, installation data, and/or software version of a particular hydraulic fracturing pump.

The second GUI 600 may include operational data 614. Operational data 614 may include operating data of a particular hydraulic fracturing pump, for example, hours in operation, hours on a type of fuel, engine cycles, among other aspects of hydraulic fracturing pump operation. The second GUI 600 may include maintenance data 616. The maintenance data 616 may include maintenance time for varying aspects of a hydraulic fracturing pump. The supervisory controller may determine when to perform maintenance on a hydraulic fracturing pump based on different aspects of the hydraulic fracturing pump as described above. When the supervisory controller determines a time for maintenance, the supervisory controller may include a prompt in the second GUI 600 indicating maintenance is required. Depending on the type of maintenance and/or other factors, the supervisory controller may prevent further use of the hydraulic fracturing pump, until maintenance is performed. The performance of maintenance may be indicated based on selecting a reset or other button under maintenance data. The performance of maintenance may also be determined automatically by components, e.g., a controller, of a hydraulic fracturing pump, and such determinations may be communicated to the supervisory controller.

The second GUI 600 may additionally include an idle button 620 and/or a stop button 618. Selecting the idle button 620 during non-operation may cause the associated hydraulic fracturing pump to enter an idle state. Selecting the stop button 618 during operation or idle may cause the associated hydraulic fracturing pump to enter a stop state or cease operation.

The supervisory controller may include, generate, or determine one or more corresponding or associated displays, pages, or GUIs for the overall wellsite. As noted, a pump profile may include a position or location of a hydraulic fracturing pump. The supervisory controller may generate a third GUI 700 to indicate the position, location, coordinates, and/or other aspects of hydraulic fracturing pumps at the wellsite. The third GUI 700 may include a block or representation 704 of each of the hydraulic fracturing pumps. Each block or representation 704 may indicate the location of each hydraulic fracturing pump. The block or representation 704 may include a pump identification number 702 to indicate such a location. In another embodiment, letters or other indicators may be utilized to indicate position or location. Each block or representation 704 may include other data relating to a hydraulic fracturing pump, such as BPM, discharge pressure, and/or suction pressure. The third GUI 700 may further include a total pump rate sum 706 flowing to a wellhead and total a blender discharge 708 flowing from a blender unit. The third GUI 700 may additionally include an idle all button 712 and/or a stop all button 710. Selecting the idle all button 712 during non-operation may cause all the hydraulic fracturing pumps to enter an idle state. Selecting the stop all button 712 during operation or idle may cause all the hydraulic fracturing pumps to enter a stop state or cease operation.

References are made to block diagrams of systems, methods, apparatuses, and computer program products according to example embodiments. It will be understood that at least some of the blocks of the block diagrams, and combinations of blocks in the block diagrams, may be implemented at least partially by computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, special purpose hardware-based computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create means for implementing the functionality of at least some of the blocks of the block diagrams, or combinations of blocks in the block diagrams discussed.

These computer program instructions may also be stored in a non-transitory machine-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the machine-readable memory produce an article of manufacture including instruction means that implement the function specified in the block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide task, acts, actions, or operations for implementing the functions specified in the block or blocks.

One or more components of the systems and one or more elements of the methods described herein may be implemented through an application program running on an operating system of a computer. They may also be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, mini-computers, mainframe computers, and the like.

Application programs that are components of the systems and methods described herein may include routines, programs, components, data structures, etc. that may implement certain abstract data types and perform certain tasks or actions. In a distributed computing environment, the application program (in whole or in part) may be located in local memory or in other storage. In addition, or alternatively, the application program (in whole or in part) may be located in remote memory or in storage to allow for circumstances where tasks may be performed by remote processing devices linked through a communications network.

Although only a few exemplary embodiments have been described in detail herein, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of the embodiments of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of the embodiments of the present disclosure as defined in the following claims.

This is a continuation of U.S. Non-Provisional application Ser. No. 17/892,479, filed Aug. 22, 2022, titled “SYSTEMS AND METHODS OF UTILIZATION OF A HYDRAULIC FRACTURING UNIT PROFILE TO OPERATE HYDRAULIC FRACTURING UNITS,” which is a continuation of U.S. Non-Provisional application Ser. No. 17/301,475, filed Apr. 5, 2021, titled “SYSTEMS AND METHODS OF UTILIZATION OF A HYDRAULIC FRACTURING UNIT PROFILE TO OPERATE HYDRAULIC FRACTURING UNITS,” now U.S. Pat. No. 11,466,680, issued Oct. 11, 2022, which claims priority to and the benefit of, U.S. Provisional Application No. 62/705,628, filed Jul. 8, 2020, titled “USE OF A PUMP PROFILER AND HEALTH MONITORING FUNCTION TO OPERATE HYDRAULIC FRACTURING PUMPS AND ASSOCIATED METHODS,” and U.S. Provisional Application No. 62/705,357, filed Jun. 23, 2020, titled “THE USE OF A PUMP PROFILER AND HEALTH MONITORING FUNCTION TO OPERATE HYDRAULIC FRACTURING PUMPS AND ASSOCIATED METHODS,” the disclosures of which are incorporated herein by reference in their entireties.

In the drawings and specification, several embodiments of systems and methods to operate hydraulic fracturing pumps for a hydraulic fracturing system or wellsite hydraulic fracturing system have been disclosed, and although specific terms are employed, the terms are used in a descriptive sense only and not for purposes of limitation. Embodiments of systems and methods have been described in considerable detail with specific reference to the illustrated embodiments. However, it will be apparent that various modifications and changes may be made within the spirit and scope of the embodiments of systems and methods as described in the foregoing specification, and such modifications and changes are to be considered equivalents and part of this disclosure. 

What is claimed:
 1. A method of utilizing a hydraulic fracturing unit profile to operate a plurality of hydraulic fracturing units for a hydraulic fracturing system, the method comprising: determining a status of a pump controller of a pump of each of the plurality of hydraulic fracturing units; in response to the status of the pump controller of each of the plurality of hydraulic fracturing units: obtaining pump maintenance data and pump event and alarm history data for the pump of each of the plurality of hydraulic fracturing units, and determining a pump maintenance cycle for the pump of each of the plurality of hydraulic fracturing units based on the pump maintenance data and the pump event and alarm history data; determining a status of an engine controller of an engine of each of the plurality of hydraulic fracturing units; building a hydraulic fracturing unit profile for each of the plurality of hydraulic fracturing units including pump and engine data and characteristics; and determining a subset of the plurality of hydraulic fracturing units to use for a hydraulic fracturing operation based on each hydraulic fracturing unit profile.
 2. The method of claim 1, wherein the hydraulic fracturing unit profile for each of the plurality of hydraulic fracturing units includes one or more of: (a) pump assembly data, (b) the pump maintenance data, (c) the pump event and alarm history data, (d) the pump maintenance cycle, (e) maximum pump flow, (f) maximum pump pressure, (g) maximum pump speed, (h) engine assembly data, (i) the engine maintenance data, (j) the engine event and alarm history data, (k) the engine maintenance cycle, or (l) maximum power output.
 3. The method of claim 2, further comprising: obtaining, for the pump of each of the plurality of hydraulic fracturing units, real-time pump operation data; and obtaining, for the engine of each of the plurality of hydraulic fracturing units, real-time engine operation data.
 4. The method of claim 3, wherein the pump event and alarm history data and the engine event and alarm history data are obtained continuously and in real-time, and the method further comprising displaying each hydraulic fracturing unit profile in a graphical user interface (GUI) on a display.
 5. The method of claim 4, wherein the hydraulic fracturing unit profile for each of the plurality of hydraulic fracturing units are updated based on one or more of: (a) updated pump event and alarm history data, (b) updated engine event and alarm history data, (c) real-time pump operation data, or (d) real-time engine operation data.
 6. The method of claim 4, further comprising: determining whether to derate the pump of one of the plurality of hydraulic fracturing units based on the pump event and alarm history data, the real-time pump operation data, and the maximum power output.
 7. The method of claim 3, wherein, for each of the plurality of hydraulic fracturing units, the engine maintenance data and the engine event and alarm history data include one or more of levels of consumables associated with the engine of a corresponding hydraulic fracturing unit of the plurality of hydraulic fracturing units, age of consumables associated with the engine of the corresponding hydraulic fracturing unit, time periods of a change or maintenance of consumables associated with the engine of the corresponding hydraulic fracturing unit.
 8. The method of claim 7, further comprising: determining, for each of the plurality of hydraulic fracturing units, the life expectancy of consumables associated with the engine of the corresponding hydraulic fracturing unit based on the time periods of a change or maintenance of consumables associated with the engine corresponding hydraulic fracturing unit and the engine assembly data.
 9. The method of claim 8, further comprising, for each of the plurality of hydraulic fracturing units: monitoring the levels of consumables and age associated with the engine of the corresponding hydraulic fracturing unit; determining whether a consumable level of the levels of consumables is low; and determining whether the consumable reached a low consumable level at an unexpected time based on one or more of life expectancy, an age of the consumable, level of the consumable, or the engine assembly data.
 10. The method of claim 9, further comprising: in response to a determination that a failure occurred at the unexpected time: shutting down the engine of the corresponding hydraulic fracturing unit; and initiating maintenance of the engine of the corresponding hydraulic fracturing unit.
 11. The method of claim 8, further comprising: monitoring, for each of the plurality of hydraulic fracturing units, the levels of consumables and age associated with the engine of the corresponding hydraulic fracturing unit; determining whether a failure of a consumable has occurred; and determining whether the failure occurred at an unexpected time based on one or more of life expectancy, an age of the consumable, level of the consumable, or engine assembly data.
 12. The method of claim 11, further comprising: in response to a determination that the failure occurred at the unexpected time: shutting down the engine of the corresponding hydraulic fracturing unit; and initiating maintenance of the engine of the corresponding hydraulic fracturing unit.
 13. The method of claim 3, wherein a supervisory controller is configured to: obtain data, perform the determinations, and build the hydraulic fracturing unit profile for each of the plurality of hydraulic fracturing units.
 14. A method of utilizing a hydraulic fracturing unit profile to operate a plurality of hydraulic fracturing units for a hydraulic fracturing system, the method comprising: providing a supervisory controller positioned to obtain data from a pump controller of a pump of each of the plurality of hydraulic fracturing units and an engine controller of an engine of each of the plurality of hydraulic fracturing units; determining a status of the pump controller of each of the plurality of hydraulic fracturing units via the supervisory controller; in response to the status of the pump controller of each of the plurality of hydraulic fracturing units: obtaining pump maintenance data and pump event and alarm history data for the pump of each of the plurality of hydraulic fracturing units, and determining a pump maintenance cycle for the pump of each of the plurality of hydraulic fracturing units based on the pump maintenance data and the pump event and alarm history data; determining a status of the engine controller of each of the plurality of hydraulic fracturing units via the supervisory controller; building a hydraulic fracturing unit profile via the supervisory controller for each of the plurality of hydraulic fracturing units including pump and engine data and characteristics; and determining a subset of the plurality of hydraulic fracturing units to use for a hydraulic fracturing operation via the supervisory controller based on each hydraulic fracturing unit profile.
 15. The method of claim 14, wherein the hydraulic fracturing unit profile for each of the plurality of hydraulic fracturing units includes one or more of: (a) pump assembly data, (b) the pump maintenance data, (c) the pump event and alarm history data, (d) the pump maintenance cycle, (e) maximum pump flow, (f) maximum pump pressure, (g) maximum pump speed, (h) engine assembly data, (i) the engine maintenance data, (j) the engine event and alarm history data, (k) the engine maintenance cycle, or (l) maximum power output.
 16. The method of claim 14, further comprising: obtaining, for the pump of each of the plurality of hydraulic fracturing units, real-time pump operation data; and obtaining, for the pump of each of the plurality of hydraulic fracturing units, real-time engine operation data.
 17. The method of claim 16, wherein the pump event and alarm history data and engine event and alarm history data are obtained continuously and in real-time, and the method further comprising displaying each hydraulic fracturing unit profile in a graphical user interface (GUI) on a display.
 18. The method of claim 14, wherein the hydraulic fracturing unit profile for each of the plurality of hydraulic fracturing units are updated based on one or more of: (a) updated pump event and alarm history data, (b) updated engine event and alarm history data, (c) real-time pump operation data, or (d) real-time engine operation data.
 19. The method of claim 18, further comprising: determining whether to derate the pump of one of the plurality of hydraulic fracturing units based on the pump event and alarm history data, the real-time pump operation data, and the maximum power output.
 20. The method of claim 14, wherein, for each of the plurality of hydraulic fracturing units, the engine maintenance data and the engine event and alarm history data include one or more of levels of consumables associated with the engine of a corresponding hydraulic fracturing unit of the plurality of hydraulic fracturing units, age of consumables associated with the engine of the corresponding hydraulic fracturing unit, time periods of a change or maintenance of consumables associated with the engine of the corresponding hydraulic fracturing unit.
 21. The method of claim 20, further comprising: determining, for each of the plurality of hydraulic fracturing units, the life expectancy of consumables associated with the engine of the corresponding hydraulic fracturing unit based on the time periods of a change or maintenance of consumables associated with the engine of the corresponding hydraulic fracturing unit and engine assembly data.
 22. The method of claim 20, further comprising, for each of the plurality of hydraulic fracturing units: monitoring levels of consumables and age associated with the engine of the corresponding hydraulic fracturing unit; determining whether a consumable level of the levels of consumables is low; and determining whether the consumable reached a low consumable level at an unexpected time based on one or more of life expectancy, an age of the consumable, level of the consumable, or engine assembly data.
 23. The method of claim 22, further comprising: in response to a determination that a failure occurred at the unexpected time: shutting down the engine of the corresponding hydraulic fracturing unit; and initiating maintenance of the engine of the corresponding hydraulic fracturing unit.
 24. The method of claim 20, further comprising: monitoring, for each of the plurality of hydraulic fracturing units, the levels of consumables and age associated with the engine of the corresponding hydraulic fracturing unit; determining whether a failure of a consumable has occurred; and determining whether the failure occurred at an unexpected time based on one or more of life expectancy, an age of the consumable, level of the consumable, or engine assembly data.
 25. The method of claim 24, further comprising: in response to a determination that the failure occurred at the unexpected time: shutting down the engine of the corresponding hydraulic fracturing unit; and initiating maintenance of the engine of the corresponding hydraulic fracturing unit.
 26. A method of utilizing a hydraulic fracturing unit profile to operate a plurality of hydraulic fracturing units for a hydraulic fracturing system, the method comprising: providing a supervisory controller positioned to communicate with a pump controller of a pump of each of the plurality of hydraulic fracturing units and an engine controller of an engine of each of the plurality of hydraulic fracturing units and configured to obtain data from the pump controller and the engine controller of each of the plurality of hydraulic fracturing units; determining a status of the pump controller of each of the plurality of hydraulic fracturing units via the supervisory controller; in response to the status of pump controller of each of the plurality of hydraulic fracturing units: obtaining pump maintenance data and pump event and alarm history data for the pump of each of the plurality of hydraulic fracturing units, and determining a pump maintenance cycle for the pump of each of the plurality of hydraulic fracturing units based on the pump maintenance data and the pump event and alarm history data; determining a status of the engine controller of each of the plurality of hydraulic fracturing units via the supervisory controller; building a hydraulic fracturing unit profile via the supervisory controller for each of the plurality of hydraulic fracturing units including pump and engine data and characteristics; and determining a subset of the plurality of hydraulic fracturing units to use for a hydraulic fracturing operation via the supervisory controller based on each hydraulic fracturing unit profile.
 27. The method of claim 26, further comprising: obtaining, for the pump of each of the plurality of hydraulic fracturing units, real-time pump operation data; and obtaining, for the engine of each of the plurality of hydraulic fracturing units, real-time engine operation data.
 28. The method of claim 27, wherein the hydraulic fracturing unit profile for each of the plurality of hydraulic fracturing units are updated based on one or more of: (a) updated pump event and alarm history data, (b) updated engine event and alarm history data, (c) real-time pump operation data, or (d) real-time engine operation data.
 29. A method of utilizing a hydraulic fracturing unit profile to operate a hydraulic fracturing unit for a hydraulic fracturing system, the method comprising: in response to a status of the pump controller: obtaining pump maintenance data and pump event and alarm history data, obtaining real-time pump operation data of the pump, and determining a pump maintenance cycle based on the pump maintenance data and pump event and alarm history data; determining a status of an engine controller of an engine of the hydraulic fracturing unit; building a hydraulic fracturing unit profile for the hydraulic fracturing unit including pump and engine data and characteristics; and determining whether to use the hydraulic fracturing unit for a hydraulic fracturing operation based on the hydraulic fracturing unit profile.
 30. The method of claim 29, wherein the hydraulic fracturing profile for the hydraulic fracturing unit is updated based on one or more of: (a) updated pump event and alarm history data, (b) updated engine event and alarm history data, (c) real-time pump operation data, or (d) real-time engine operation data. 